Skip to content

Add ddev release port-commit command#23680

Closed
AAraKKe wants to merge 11 commits into
masterfrom
aarakke/ddev-port-commit
Closed

Add ddev release port-commit command#23680
AAraKKe wants to merge 11 commits into
masterfrom
aarakke/ddev-port-commit

Conversation

@AAraKKe
Copy link
Copy Markdown
Contributor

@AAraKKe AAraKKe commented May 12, 2026 •
edited
Loading

What does this PR do?

Adds ddev release port-commit: cherry-picks a commit onto a target branch, pushes a <user>/port-<sha>-to-<target> branch, and opens a PR.

Motivation

Brings an existing personal backport script into ddev so the flow is consistent, discoverable, and reuses ddev's git/GitHub helpers.

The workflow is built as an ordered list of PortStep objects (fetch, checkout, branch, cherry-pick, in-toto sweep, commit, push, open PR). Each step has a uniform describe / planned_commands / execute interface, so adding or reordering steps is a one-line change in build_port_steps.

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
  • If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

@AAraKKe AAraKKe added the qa/skip-qa Automatically skip this PR for the next QA label May 12, 2026
@dd-octo-sts dd-octo-sts Bot added the ddev label May 12, 2026
@datadog-datadog-prod-us1

This comment has been minimized.

Sign in to view
@codecov
Copy link
Copy Markdown

codecov Bot commented May 12, 2026 •
edited
Loading

Codecov Report

❌ Patch coverage is 95.71899% with 39 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.91%. Comparing base (2f31885) to head (d87567e).
⚠️ Report is 8 commits behind head on master.

Additional details and impacted files
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@dd-octo-sts
Copy link
Copy Markdown
Contributor

dd-octo-sts Bot commented May 13, 2026

Validation Report

All 20 validations passed.

Show details
Validation Description Status
agent-reqs Verify check versions match the Agent requirements file ✅
ci Validate CI configuration and Codecov settings ✅
codeowners Validate every integration has a CODEOWNERS entry ✅
config Validate default configuration files against spec.yaml ✅
dep Verify dependency pins are consistent and Agent-compatible ✅
http Validate integrations use the HTTP wrapper correctly ✅
imports Validate check imports do not use deprecated modules ✅
integration-style Validate check code style conventions ✅
jmx-metrics Validate JMX metrics definition files and config ✅
labeler Validate PR labeler config matches integration directories ✅
legacy-signature Validate no integration uses the legacy Agent check signature ✅
license-headers Validate Python files have proper license headers ✅
licenses Validate third-party license attribution list ✅
metadata Validate metadata.csv metric definitions ✅
models Validate configuration data models match spec.yaml ✅
openmetrics Validate OpenMetrics integrations disable the metric limit ✅
package Validate Python package metadata and naming ✅
readmes Validate README files have required sections ✅
saved-views Validate saved view JSON file structure and fields ✅
version Validate version consistency between package and changelog ✅

View full run

@AAraKKe
Copy link
Copy Markdown
Contributor Author

AAraKKe commented May 13, 2026

Closing in favor of two stacked PRs (async-client refactor + port-commit command on top), managed via Graphite.

@AAraKKe AAraKKe closed this May 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

ddev qa/skip-qa Automatically skip this PR for the next QA

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@AAraKKe